@zth I would assume this will require some LSP server changes as well?

@zth I would assume this will require some LSP server changes as well?

Each platform package will expose binary locations, making it easier to handle.

import { binDir, binPaths } from "@rescript/linux-x64"

@cknitt With the current configuration, we have to copy the runtime directory for every platform.

Or we can just extract @rescript/runtime as the default dependency.

Kinda unreliable fix: a4eb634

Or we can just extract @rescript/runtime as the default dependency.

I think that would definitely make sense. 👍

Hi @cometkim, this didn't really work for when I installed the packages using a relative path:

"dependencies": {
    "rescript": "../rescript"
  },
  "devDependencies": {
    "@rescript/darwin-arm64": "../rescript/packages/@rescript/darwin-arm64"
  },

bunx rescript:

>>>> Start compiling
TypeError: Cannot read properties of undefined (reading 'toString')
    at acquireBuild (file:///Users/nojaf/Projects/rescript/cli/common/bsb.js:57:53)
    at delegate (file:///Users/nojaf/Projects/rescript/cli/common/bsb.js:76:12)
    at Module.build (file:///Users/nojaf/Projects/rescript/cli/common/bsb.js:487:5)
    at file:///Users/nojaf/Projects/rescript/cli/rescript.js:134:7
Error: spawn /Users/nojaf/Projects/rescript/packages/@rescript/darwin-arm64/bin/rescript.exe ENOENT

zsh: no such file or directory: /Users/nojaf/Projects/rescript/packages/@rescript/darwin-arm64/bin/rescript.exe

I'm guessing I'm only having this because the symlink thing doesn't work locally.
However, I really use this often, so it would be great if this still worked.

I'm also a fan of having @rescript/runtime. That would be in dependencies, where rescript itself could move to devDependencies again.

Once I downloaded the packages from the GitHub action, it did all work as expected.
I'm able to to run bunx rescript and bunx bsc as I used to.

Tooling broke as I suspected, but we can deal with that. Wouldn't consider that a blocker.

Workaround for tooling would be to set:

    "rescript.settings.platformPath": "/Users/my-user/Projects/my-project/node_modules/@rescript/darwin-arm64/bin"

this didn't really work for when I installed the packages using a relative path:

@nojaf This is expected behavior of file: protocol of npm/yarn/pnpm/bun. Because the protocol doesn't handle its transitive dependencies.

Make sure your package manager supports other protocols that can handle it properly. If you are using Yarn, you can use portal: protocol instead.

git or tgz protocol might be a workaround.

Well, that is not really a satisfying answer. Can't we just copy the actual binaries to escript/packages/@rescript/darwin-arm64/bin? That way it all works like before right?

Getting rid of symlinks would be good. I'll try.

But then I'm not sure about the file or link still.